Wireless chat automatic status tracking

ABSTRACT

A technique and apparatus to provide status tracking of presence and/or location of a mobile, wireless device to a requesting entity even outside of a particular wireless system. This allows wireless service providers the ability to monitor and log changes in the status of mobile stations within and/or outside their networks. Embodiments are disclosed wherein presence and/or location information is provided to entities outside of a particular servicing wireless network using the mechanisms of call processing components of a mobile network (e.g., call setup procedures), and using standard mechanisms currently available to any appropriately conforming Mobile Switching Center (MSC) element. In one disclosed embodiment, a wireless chat tracking system is implemented which utilizes a change in mobile registration status to automatically notify a chat group system outside the wireless network of current status information activity regarding a relevant device, e.g., registration activity or inactivity timeout. In the wireless chat automatic status tracking system, a registration notification (REGNOT) message is either explicitly forwarded or copied to an external IP based application (e.g., to a mobile chat group system). The change in mobile registration is communicated via a suitable signaling link (e.g., SS7, TCP/IP, etc.) between a Home Location Register (HLR) and the chat group system. Therefore, instead of a conventionally closed system using SS7 messages, REGNOT messages are pushed out over TCP/IP connections to external applications (e.g., chat servers) to automatically notify the external system of the location of a particular user.

[0001] This application is related to and claims priority fromco-pending U.S. Provisional Application No. 60/196,104, entitled “MobileActivity Status Tracker” to Wallace et al., filed on Apr. 11, 2000; fromco-pending U.S. Provisional Application No. 60/196,099, entitled“Wireless Chat Status Tracking” to Ung et al., filed on Apr. 11, 2000;and from co-pending U.S. application Ser. No. 09/576,022, entitled“Mobile Activity Status Tracker” to Wallace et al., filed on May 23,2000, the entirety of all three of which are expressly incorporatedherein by reference.

BACKGROUND OF THE INVENTION

[0002] 1. Field of the Invention

[0003] This invention relates generally to wireless carriers, Internetservice providers (ISPs), information content deliveryservices/providers, portal sites for mobile-terminated hosting of chatgroups, and/or Internet chat session hosts. More particularly, itrelates to the gateway perspective of mobile device functions such asANSI-41 automatic registration, real-time Internet message billing,real-time wireless message billing, messaging in general, wireless chat,and/or Internet chat.

[0004] 2. Background of Related Art

[0005] The present invention relates to improvements to mobile wirelesssystems, which currently include mobility management, IS-41 mobilitymanagement, and/or registration systems, to support, e.g., Internetchat, ICQ, etc.

[0006] Up to this point, in a Wireless & Internet chat group system, achat member must manually notify the system when he/she desires to goon-line or off-line. This invention enables a wireless carrier and/orInternet service provider to introduce a Wireless Intelligent Network(WIN) service that allows a chat room or session system to beautomatically notified when the subscriber is on-line or off-line. Thiswill allow, for example, the chat system to continually andautomatically notify the subscribers of the chat group or a “buddy list”about a participant's status in a chat room/session at any time. ThisWIN service will be applicable to both prepaid and postpaid IS-41networks.

[0007] Currently no system is known to provide such WIN service forwireless devices. Existing systems allow the landline internetsubscriber to automatically notify the chat group when the subscribergoes on-line or off-line.

[0008] Existing technologies have not addressed the concept of automaticnotification for wireless chat participants. Without this feature,members in the chat group are not aware of the member's actual status.The wireless participants have to remember to notify the chat group orbuddies of his/her availability.

[0009] As is known, presence information and location informationregarding a particular wireless device is recorded in a Home LocationRegister for the relevant wireless network.

[0010]FIG. 10 shows a conventional stand-alone Home Location Register(SHLR) architecture and message flow of a Mobile RegistrationNotification message (REGNOT).

[0011] In FIG. 10, a first wireless network 1060 includes a mobileswitching center MSC 1010 and a stand-alone Home Location Register(SHLR) 1040. The SHLR 1040 and the MSC 1010 communicate over thecellular telephony network (and perhaps the PSTN when calls areconnected to a land-line switch or calls need to be delivered via atrunk line that routes through a PSTN) via one or more switchingtransfer points (STPs) 1030. The protocol used for communication isIS-41 or GSM-MAP over signaling system No. 7 (SS7).

[0012] The service provider is typically given maintenance andconfiguration proprietary access to the database stored in the SHLRusing an Operations and Maintenance Processor (OMP) and provisioningterminal console 1050, which may communicate with the SHLR using apoint-to-point link, e.g., an X.25 link, an RS-232 link, or a TCP/IPlink. Communications from the OMP 1050 typically relate to maintenanceand configuration only, and do not relate to operational functions ofthe relevant wireless network.

[0013] A second wireless network 1070 servicing another wireless device1090 includes another MSC 1020, and utilizes one or more STPs 1030 inthe SS7network.

[0014] In the given scenario, assume that the wireless device 1090 incommunication with the second wireless network 1070 is serviced by theservice provider of the first wireless network 1060. Thus, presence andlocation information regarding the second wireless device 1090 is storedand updated in the SHLR 1040 corresponding to its servicing network.

[0015] To communicate presence and location information to the ‘home’register of the second wireless device 1090, a MOBILE REGISTRATIONmessage (1.) is sent in accordance with Signaling System #7 (SS7)standards using IS-41C protocol messages through the second wirelessnetwork 1070 to the MSC 1020 of the second wireless network 1070. The‘presence’ of a wireless device relates to the wireless device beingpowered ON and reachable in the relevant wireless network.

[0016] The MSC 1020 forwards the MOBILE REGISTRATION message (1.) uponreceipt to the STP 1030 as an IS-41 REGISTRATION NOTIFICATION (REGNOT)message (2.).

[0017] The STP 1030 forwards the REGNOT message (3.) to the appropriateSHLR 1040 servicing that particular wireless device 1090.

[0018] In this way, the Home Location Register of a particular wirelessdevice 1040 is provided with presence and location information regardingthe whereabouts and registration activity of a particular subscriber(e.g., wireless device 1090).

[0019]FIG. 10 relates to a Home Location Register which is installed asa separate network element. Using a SHLR 1040 as shown in FIG. 10, theSHLR 1040 must communicate with the associated MSC 1010 using SS7signaling through the STP 1030. Presence and location information isupdated in a subscriber's Home Location Register in a similar mannerwhen the Home Location Register is integrated onto a common platformwith the MSC element. This configuration is known as an integrated HomeLocation Register (I-HLR).

[0020]FIG. 11 shows a conventional integrated Home Location Register(I-HLR) architecture and message flow of a Mobile RegistrationNotification message (REGNOT) allowing proprietary communicationsbetween elements such as the MSC and I-HLR operating on a commonplatform.

[0021] In particular, as shown in FIG. 11, a MOBILE REGISTRATION message(1.) is sent to the MSC 1020 providing access to the roaming wirelessdevice 1090, and the MSC 1020 forwards the REGNOT message (2.) to therelevant STPs 1030 as shown in FIG. 10. However, instead of forwardingthe REGNOT message (3.) to the SHLR 1040 as shown in FIG. 10, the REGNOTmessage (3.) in FIG. 11 is forwarded to the common platform includingboth the MSC 1110 and the I-HLR 1140. The MSC 1110 and I-HLR 1140 maycommunicate with one another using any desired proprietarycommunications protocol, without need to conform to the SS7signalingprotocol at that point. Nevertheless, the I-HLR 1140 is updated withpresence and location information regarding the roaming wireless device1090.

[0022] In the conventional scenario, presence and location informationis restricted to use by the ‘home’ service provider of a particularwireless device. Using conventional signaling protocols, other wirelessnetworks are not provided with presence and location informationregarding wireless devices other than those which subscribe to itsservices. The presence and location information is conventional usedonly by the home service provider for routing of call information (e.g.,establishing a voice connection to a mobile wireless device).

[0023] Accordingly, there is a need for providing presence and locationinformation to entities other than just those servicing a particularwireless device, thus enabling a new host of network services andapplications.

SUMMARY OF THE INVENTION

[0024] In accordance with the principles of the present invention, in ashort message service center, a module for permitting automatic statustracking of a wireless chat participant by an application external to aservice provider including said short message service center, a REGNOTand/or MSInactive handler comprises a registration notification and/oran MS inactivity messages receiver, and a registration/inactive messageforwarder to forward a registration notification and/or MS inactivitymessage received by a mobile switching center over an Internetconnection.

[0025] A method for automatically notifying an external chat server of apresence of a chat session participant in accordance with another aspectof the present invention comprises receiving an IS-41 conformingregistration notification and MS inactive messages from one of a mobiletelephony network, mobile switching center, I-HLR, and S-HLR or STP, andautomatically forwarding the IS-41 conforming registration notificationand MS inactive messages over an Internet connection to an external chatserver.

BRIEF DESCRIPTION OF THE DRAWINGS

[0026] Features and advantages of the present invention will becomeapparent to those skilled in the art from the following description withreference to the drawings. Note that for simplicity of explanation, onlya REGNOT message is shown in the figures. However, an MS inactivity(MSInactive) message may be conveyed in the same way as as the REGNOTmessage. In the drawings:

[0027]FIG. 1 shows an exemplary architecture and information flow of amobile activity status tracker (MAST) system, in accordance with theprinciples of the present invention.

[0028]FIG. 2 is a more detailed architecture and information flow of anembodiment of a MAST system corresponding to a stand-alone Home LocationRegister (SHLR) including a registration notification forwardingmechanism utilizing message flows in conformance with SS7 standards andIS-41 standards, in accordance with the principles of the presentinvention.

[0029]FIG. 2A shows a block diagram of the basic elements of anexemplary MAST system shown in FIG. 2.

[0030]FIG. 3 is a detailed architecture and information flow of anembodiment of a MAST system corresponding to an integrated Home LocationRegister (I-HLR) including a registration notification forwardingmechanism integrated with a mobile switching center (MSC) on a commonplatform, utilizing message flows in conformance with SS7 standards andIS-41 standards, in accordance with the principles of the presentinvention.

[0031]FIG. 4 is a detailed architecture and information flow of anembodiment of a MAST system corresponding to a stand-alone Home LocationRegister (SHLR) including a Registration Notification copy function in asignaling transfer point (STP) and a TCP/IP connection (or SS7connection) to the MAST application, particularly useful in wirelessnetworks having HLRs which do not include a registration notificationforwarding mechanism, in accordance with the principles of the presentinvention.

[0032]FIG. 5A is a simplified depiction of relevant parameters of aMobile Registration Notification (REGNOT) message in conformance withSS7 and IS-41 standards utilized for determination of locationinformation in a MAST system, in accordance with the principles of thepresent invention.

[0033]FIG. 5B is a detailed depiction of all conventional parameters ofa REGNOT message.

[0034]FIG. 6 is a simplified depiction of relevant parameters of aMobile Subscriber Inactive message in conformance with SS7 and IS-41standards utilized for determination of inactive presence information ina MAST system, in accordance with the principles of the presentinvention.

[0035]FIG. 6B is a detailed description of the otherwise conventionalMSInactive message parameters.

[0036]FIG. 7A is a simplified depiction of relevant parameters such aslocation in an exemplary Internet Protocol (IP) message sent from theMAST system to an application server (e.g., a Chat Server) via theInternet, in accordance with the principles of the present invention.

[0037]FIG. 7B is a simplified depiction of relevant parameters inanother exemplary IP message such as a log of past presence and locationinformation for a particular wireless device sent from the MAST systemto an application server (e.g., a law enforcement authority) via theInternet, in accordance with the principles of the present invention.

[0038]FIG. 8 shows an exemplary Mobile Station Identity (MSID) orderedtable, in accordance with the principles of the present invention.

[0039]FIG. 9 shows an exemplary process by which the parsed messageportions are processed.

[0040]FIG. 10 shows a conventional stand-alone Home Location Register(SHLR) architecture and message flow of a Mobile RegistrationNotification message (REGNOT).

[0041]FIG. 11 shows a conventional integrated Home Location Register(I-HLR) architecture and message flow of a Mobile RegistrationNotification message (REGNOT) allowing proprietary communicationsbetween elements such as the MSC and I-HLR operating on a commonplatform.

[0042]FIG. 12 shows an exemplary service implementation showing wirelesschat status tracking providing an automatic on-line or off-linenotification in a chat scenario using techniques and apparatus inaccordance with the principles of the present invention.

[0043]FIG. 13 shows a block diagram of the SMSC shown in FIG. 12,including a REGNOT/MSInactive message receiver, a REGNOT/MSInactiveforwarder, and an optional REGNOT/MSInactive copier, in accordance withthe principles of the present invention.

DETAILED DESCRIPTION OF ILLUSTRATIVE EMBODIMENTS

[0044] The present invention relates to a technique and apparatus toprovide status tracking of presence and/or location of a mobile,wireless device to a requesting entity even outside of a particularwireless system. This allows wireless service providers the ability tomonitor and log changes in the status of mobile stations within and/oroutside their networks enabling the development of multiple applicationsand network services. Embodiments are disclosed wherein presence and/orlocation information is provided to entities outside of a particularservicing wireless network using the mechanisms of call processingcomponents of a mobile network (e.g., call setup procedures), and usingstandard mechanisms currently available to any appropriately conformingMobile Switching Center (MSC) element. An embodiment implementing awireless chat automatic status tracking system and method is alsodisclosed.

[0045] Mobile presence and location are key concepts for location-basedservices and applications which require knowledge of mobilestation/subscriber availability. Currently, conventional systems do notprovide such wireless intelligent network (WIN) service for wirelessdevices.

[0046] It is important to note that existing systems and techniques havebeen conventionally located outside of a wireless network. As such, theexisting systems have not been privy to, nor had the need to be privyto, triggers needed to obtain true mobile presence or locationinformation.

Mobile Activity Status Tracker (MAST)

[0047] One series of disclosed embodiments relate to a softwareapplication package which tracks and reports status and activity ofmobile wireless devices in a wireless network using mobile registrationmessage, inactivity message forwarding, and/or mobile automaticnotification of subscriber status to TCP/IP entities. This embodiment ofa mobile activity status tracker is referred to herein as a MobileActivity Status Tracker (MAST).

[0048] In accordance with the principles of the present invention,status changes that are recorded are sent via TCP/IP communications toother service provider-specific applications. The MAST system duplicatesthe same or similar information of a corresponding HLR, but is availableas an external database entity which functions and communications arenot restricted by SS7 standards.

[0049] Tracking in accordance with the principles of the presentinvention utilizes registration/de-registration activity of mobilestations. Utilizing status changes for a particular mobile station, keyevents can be noted regarding presence and/or location of the particularmobile station.

[0050] The MAST application offers entities (e.g., Internet and others)outside of a wireless infrastructure the ability to receive presenceand/or location information regarding a particular mobile station tonetwork entities outside of that which is servicing a particularwireless device. As disclosed, the MAST application has the ability topull presence and/or location information or to push presence and/orlocation information to a requesting entity as desired.

[0051] Certain capabilities such as registration notification forwardingmechanisms/Registration Notification Forward Message and SMPP clientwhich are basic to this application, are described in detail in twopending U.S. Applications by the same Assignee as the present case. Inparticular, an exemplary SMSC is described in co-pending and co-ownedU.S. appl. Ser. No. 09/322,929, entitled “Short Message ServiceNotification Between Multiple Short Message Service Centers”, filed Jun.1, 1999, by Timothy J. Lorello and Reuben D. Hart, the entirety of whichis explicitly incorporated herein by reference. Moreover, an exemplaryPrepaid functionality and architecture is described in co-pending andco-owned U.S. appl. Ser. No. 09/533,805, entitled “Prepaid CallManagement In Intelligent Network”, filed Mar. 23, 2000, by ElizabethCountryman, Timothy J. Lorello, Mark Titus, and Dara Ung, the entiretyof which is explicitly incorporated herein by reference.

[0052] The Mobile Activity Status Tracker (MAST) is a Service PackageApplication (SPA) that allows wireless service providers to monitor andlog changes in the status of mobile stations within their networks. Thestatus changes that are recorded are sent via TCP/IP to other serversfor service provider-specific applications. The tracking involves theregistration/de-registration activity and location of the mobilestations. The tracking need not track call-specific information, e.g.,called telephone numbers or information regarding conversationssustained by the tracked wireless subscribers.

[0053] Some disclosed embodiments relate to the use of a Home LocationRegister (HLR) which is integrated with a Mobile Switching Center (MSC)on a common platform, referred to herein as Integrated Home LocationRegisters (I-HLRs) commercially available from LUCENT TECHNOLOGIES INC.in Murray Hill, N.J. Other embodiments relate to the use of astand-alone HLR separate from the MSC platform, referred to herein asStand alone HLR's (S-HLR). All types of HLRs are collectively referredto herein as an HLR.

[0054] The disclosed MAST SPA is implemented on an Advantage ServiceControl Point (SCP) Wireless Intelligent Network Platform, commerciallyavailable from LUCENT TECHNOLOGIES INC. The SCP provides the requiredANSI SS7 and TCP/IP protocol support and Service Circuit Handlers (SCH)for the MAST SPA.

[0055] In accordance with the principles of the present invention, theMAST SPA receives mobile activity notifications from an HLR, andforwards selected parameters upon request or configuration to serversexternal to the wireless network over a TCP/IP communication link (e.g.,over the Internet or over an Intranet).

[0056]FIG. 1 shows an exemplary architecture and information flow of amobile activity status tracker (MAST) system, in accordance with theprinciples of the present invention.

[0057] In particular, as shown in FIG. 1, the operation of the exemplaryMAST SPA includes the following exemplary steps:

[0058] (1) The handset exchanges activity information with the I-HLR,which in turn sends the Mobile Station Identity (MSID) of the mobilestation and a set of relevant parameters to the MAST SPA in aregistration notification forwarding mechanism message.

[0059] (2) The MAST SPA creates a temporary record for that mobilehandset based on the MSID. The MAST performs a lookup in a database ofexisting records, using the MSID as a key. If there is no record for theMSID, then the temporary record is stored in the database. If there is arecord for the same MSID, the MAST compares the temporary record withthat found in the database to determine any changes in the activitystatus of the mobile station (or any other relevant parameters). If theactivity status is the same (i.e., unchanged), the MAST overwrites theold record with the new one. On the other hand, if the activity statushas changed, the activity status of the relevant mobile wireless devicewill be Notified or Forwarded to one or more application servers havingaccess to the Internet using an appropriate TCP/IP interface andappropriate IP addresses (or other suitable protocol and communicationpath, e.g., SS7). To this end, the MAST SPA will forward a set ofselected parameters (e.g., a subset of the parameters available in thetemporary record) to one or more requesting or pre-configuredapplications servers using corresponding Internet Protocol (IP)addresses. The MAST then replaces the existing, older record with thenew, updated record.

[0060] Preferably, the MAST resides on an SCP and accepts copies ofIS-41 Registration Notification and MSInactive messages from the HLR(s).

[0061]FIG. 2 is a more detailed architecture and information flow of anembodiment of a MAST system 200 corresponding to a stand-alone HomeLocation Register (SHLR) 240 including a registration notificationforwarding mechanism utilizing message flows in conformance with SS7standards and IS-41 standards, in accordance with the principles of thepresent invention.

[0062] In particular, FIG. 2 shows a MAST system 200 implemented by aparticular service provider corresponding to a first wireless network260. The first wireless network 260 also includes an MSC 1010, and aSHLR 240.

[0063] A second wireless network 1070 is shown for completeness andperspective. The second wireless network 1070 includes an MSC 1020, andservices a wireless device 1090.

[0064] The MAST 200 provides presence and/or location informationregarding any or all subscriber's of the first wireless network toexternal entities, without the need to change current communicationstandards, e.g., utilizing otherwise conventional SS7 and IS-41communication messages.

[0065] The MAST 200 includes information similar to that contained inthe SHLR, e.g., relating to the presence and/or location of servicedwireless devices. However, in accordance with the principles of thepresent invention, the MAST 200 may include additional information,and/or logged information over time with respect to each individualsubscriber. The MAST 200 may be implemented on a same type platform asthat implementing the SHLR 240, e.g., an SCP commercially available fromLUCENT TECHNOLOGIES INC.

[0066]FIG. 2A shows a block diagram of the basic elements of anexemplary MAST system 200 shown in FIG. 2.

[0067] Importantly, the MAST 200 includes a TCP/IP interface 270 andinternal module 201 allowing appropriate operational access tosubscriber presence and/or location information maintained therein.Thus, any or all external application servers 290 (e.g., chat servers,law enforcement servers, etc.) may access subscriber presence and orlocation information regarding a wireless service provider's subscribersvia the Internet 280.

[0068] The subscriber's presence and/or location information maintainedin a subscriber presence/location database 205 may be pre-configured fortransmission to various pre-set application servers 290 via the TCP/IP(i.e., non-SS7 protocol) module 201 and associated link 270.Alternatively, presence and/or location information regarding any or allsubscriber's serviced by the MAST 200 may be provided to an applicationserver 290 upon request by the application server 290.

[0069] Referring back to FIG. 2, the particular applications which canbe implemented by the various application servers 290 is virtuallylimitless. Any application which can make use of the presence and/orlocation information regarding any or all wireless subscribers(regardless of whether or not they are inside or external to aparticular wireless network) may utilize the information contained inthe database of the MAST 200 in accordance with the principles of thepresent invention.

[0070] The message flow shown in FIG. 2 relates to that of a stand-aloneHLR 240. The message flow utilizing an integrated HLR is shown in FIG.3. The message flow in FIG. 2 is as follows.

[0071] A MOBILE REGISTRATION message (1.) is transmitted by a relevantwireless device 1090 through the host wireless network #2 1070 to itsMSC 1020. That MSC 1020 sends a MOBILE REGISTRATION NOTIFICATION(REGNOT) message (2.) to an STP 1030, which forwards a REGNOT message(3.) to the SHLR 240. Up to this point the message flow is as in theconventional system shown in FIG. 10.

[0072] However, as shown in FIG. 2, the SHLR 240 implements a messagereferred to herein as a registration notification forwarding mechanism(4. in FIG. 2). The registration forwarding mechanism (4.) forwards areceived REGNOT message (3.) back out to the STP 230 as a REGNOT message(5.), destined for the MAST 200.

[0073] The STP 230 forwards the REGNOT message (5.) from the SHLR to theMAST 200 using a REGNOT message (6.). Thus, the SHLR 240 shown in FIG. 2is an otherwise conventional SHLR, but additionally includes thefunctions necessary to implement a registration notification forwardingmechanism to forward the REGNOT message (5.) to the MAST system 200 viathe STP 230 using another forwarded REGNOT message (6.). With thearchitecture of the embodiment of FIG. 2, a service provider may need toupgrade software running on an associated SHLR 240, but need not upgradetheir MSC 1010 or STP 230 from those otherwise conventionally availableor already installed, providing significant cost savings and efficiency.

[0074] In response to the REGNOT message (6.) received from the STP1030, the MAST 200 updates its database 205 appropriately. Theinformation contained in the database 205 is then made available asappropriate over the TCP/IP link 270 to an external device, e.g., usingan Intranet or the Internet 280, e.g., to all requesters, to only somerequesters paying a particular fee for such a service, etc.

[0075] The service provider 250 is given operational and maintenanceaccess to the MAST 200 similarly to conventional access given to anSHLR, e.g., using an X.25, RS-232 or TCP/IP link.

[0076]FIG. 3 is a detailed architecture and information flow of anembodiment of a MAST system 200 corresponding to an integrated HomeLocation Register (I-HLR) including a registration notificationforwarding mechanism integrated with a mobile switching center (MSC) ona common platform, utilizing message flows in conformance with SS7standards and IS-41 standards, in accordance with the principles of thepresent invention.

[0077] In particular, FIG. 3 shows that when using an I-HLR 340, thecommunications between the MSC/I-HLR common platform and the STP 330 aretypically made over an SS7 link to the common platform, and that theelements on the common platform (e.g., the MSC 310 and the I-HLR 340)may communicate with one another in proprietary ways without the need toconform to SS7 or other external signaling requirements.

[0078] The I-HLR 340 shown in FIG. 3 is an otherwise conventional I-HLR,but additionally includes the functions necessary to implement aregistration notification forwarding mechanism to forward the REGNOTmessage (5.) to the MAST system 200 via the STP 230 using anotherforwarded REGNOT message (6.). With the architecture of the embodimentof FIG. 3, a service provider may need to upgrade software running on anassociated I-HLR 340, but need not upgrade their MSC 310 or STP 330 fromthose otherwise conventionally available or already installed.

[0079]FIG. 4 is a detailed architecture and information flow of anembodiment of a MAST system corresponding to a stand-alone Home LocationRegister (SHLR) including a Registration Notification copy function in asignaling transfer point (STP) and a TCP/IP connection (or SS7connection) to the MAST application, particularly useful in wirelessnetworks having HLRs which do not include a registration notificationforwarding mechanism, in accordance with the principles of the presentinvention.

[0080] In particular, FIG. 4 importantly shows an STP 430 includingotherwise conventional functions, but in addition includes a REGNOT copyand forward function.

[0081] The REGNOT copy and forward function in the STP 430 copies theREGNOT message (2.) received from an MSC 1020, and forwards a REGNOTcopy message (3 b.) to the MAST 200. The STP 430 also sends theotherwise conventional REGNOT message (3.) to the SHLR 1040.

[0082] The STP 430 shown in FIG. 4 is an otherwise conventional STP, butadditionally includes the functions necessary to implement a COPY andFORWARD message to generate a copy of the REGNOT message (3.) sent tothe SHLR 1040 as a copy REGNOT message (3 b.) sent to the MAST 200. Withthe architecture of the embodiment of FIG. 4, a service provider mayneed to upgrade software running on an associated STP 430, but need notupgrade their MSC(s) 1010 or SHLR(s) 1040 from those otherwiseconventionally available or already installed.

[0083] The MAST system architecture shown in FIG. 4 has the advantage ofeliminating some communications (e.g., the registration notificationforwarding mechanism trigger (4.) and the REGNOT message (5.) shown inFIG. 3), which is particularly important because the registrationnotification forwarding mechanism trigger (4.) is an enhancedproprietary feature (i.e., not standard) to some HLRs.

[0084] The service may be provided in a provisionless mode, and all thenecessary subscriber information may reside on the HLR. Thus, there ispreferably no specific subscriber provisioning necessary on the MASTSPA. Rather, the subscriber data may be maintained at the relevant HLR.The amount of memory, e.g., random access memory (RAM) and the number ofSS7 links required by the SCP platform implementing the MAST SPA may bedetermined based on the subscriber count to be supported.

[0085] For instance, as a general guideline, consider the followingexample. Assuming a load of 500,000 subscribers, one (1) registrationnotification forwarding mechanism trigger per subscriber per hour, five(5) Mobile Inactivity Triggers (MITs) per subscriber per day, 1 KB ofmemory per subscriber, and an average SS7 message length of 100 octects,the number of SS7 links required in the disclosed embodiment for thisconfiguration is approximately four (4), along with approximately 500 MBof RAM.

[0086] Use of Signaling Transfer Points (STPs) between MSCs can beimplemented in multiple I-HLR environments as well.

[0087] From the perspective of a wireless service provider, MAST allowsthe implementation of an endless array of services and/or applicationsthat can utilize presence and/or location information regarding awireless device. Specific implementations of services will depend on thecapabilities of the application servers that receive the informationfrom the MAST. For instance, knowledge of registration activity in andof itself represents a huge benefit for the service provider from amarketing perspective because it can provide additional informationregarding subscriber's habits, and general demographic data collection.

[0088] The MAST techniques and apparatus may also be used for lawenforcement purposes. For instance, data relating to mobile stationactivity may be used, e.g., as evidence to build a legal case against anoffender.

[0089] As another benefit, subscribers of a wireless service providercan be provided with an enhanced protection mechanism against fraud byallowing faster detection and/or tracking of delinquent mobile devices.

[0090] Depending upon particular parameters used, other services may beimplemented. For instance, with knowledge of the location of aparticular mobile station, a wireless service provider may implement an“Emergency Location” plan. Using such a service, mobile subscribers canhave activity information (e.g., presence and/or location information,together with date and time) relating to the use of their mobile devicetransmitted to the MAST SPA in accordance with the principles of thepresent invention. The MAST SPA will log the presence and/or locationinformation regarding relevant mobile subscribers served by theassociated HRL, and pass the logged information on to any entity on theInternet or other entity or network, providing an accurate andup-to-date information source. Using the “Emergency Location” plan, thelogged location information may be used by authorities to locate aperson associated with that particular mobile device easier.

[0091]FIG. 5A is a simplified depiction of relevant parameters of aMobile Registration Notification (REGNOT) message in conformance withSS7 and IS-41 standards utilized for determination of locationinformation in a MAST system, in accordance with the principles of thepresent invention. FIG. 5B is a detailed depiction of all conventionalparameters of a REGNOT message.

[0092] In particular, the REGNOT message parameters utilized by the MASTmay be any or all parameters included or inferred from informationwithin the standard REGNOT message shown in FIG. 5B. For instance, thecell site ID 502 and/or sector ID 504 of the cell servicing the relevantwireless device may be used to provide a location of the wirelessdevice, and date and time of a communication may be used for presenceinformation.

[0093] Other information such as power level 506 can be used to inferand further refine the location information. For instance, a lower powerlevel received by the wireless device 1090 (and/or higher power outputby the wireless device 1090) may be used to infer a longer distance fromthe relevant cell site receiving transmissions from the wireless device1090. Conversely, a higher power level might infer that the wirelessdevice 1090 is closer to the cell site. Thus, a sort of ‘poor man's GPS’can be provided to external entities regarding the location of asubscriber's wireless device.

[0094]FIG. 6 is a simplified depiction of relevant parameters of aMobile Subscriber Inactive message in conformance with SS7 and IS-41standards utilized for determination of inactive presence information ina MAST system, in accordance with the principles of the presentinvention.

[0095] In particular, a MOBILE SUBSCRIBER INACTIVE message follows thesame paths as does the REGNOT messages shown in Figs.2, 3 and 4. Whilethe REGNOT message indicates an active wireless device, the receipt of aMOBILE SUBSRIBER INACTIVE message with respect to a particularsubscriber may be logged in the database 205 of the MAST 200 as presenceinformation, i.e., that the wireless device may no longer be present.

[0096]FIG. 7A is a simplified depiction of relevant parameters such aslocation in an exemplary Internet Protocol (IP) message sent from theMAST system to an application server (e.g., a Chat Server) via theInternet, in accordance with the principles of the present invention.

[0097] The particular information contained either in the database 205of the MAST and/or which is transmitted over the TCP/IP connection 270and the Internet 280 may depend upon the particular applicationsoperating on any of the application servers 290. Rudimentary informationmay include, e.g., an IP address of the application server 290, an ID ofthe relevant mobile wireless device, presence information such as a dateand time of activity, and location information either real or inferred.Real information may include the cell site ID and/or sector ID. Inferredor extrapolated information may include, e.g., a delta distancecorresponding to a power level of the wireless device's transmitterduring a last contact.

[0098]FIG. 7B is a simplified depiction of relevant parameters inanother exemplary IP message such as a log of past presence and locationinformation for a particular wireless device sent from the MAST systemto an application server (e.g., a law enforcement authority) via theInternet, in accordance with the principles of the present invention.

[0099] For instance, as shown in FIG. 7B, presence and/or locationinformation may be logged into a historical file for eachsubscriber/wireless device. A particular mobile ID together with aseries of database entries corresponding to different REGNOT commandsand/or MOBILE SUBSCRIBER INACTIVE messages received by the MAST can beprovided to one or more particular application servers desiring suchinformation.

[0100] Alternatively, the presence and/or location informationtransmitted to a desiring application server 190 may relate to a groupof subscribers having a common attribute (e.g., most active subscribers,least active subscribers, subscribers living in a particular region,etc.).

[0101] As disclosed, activity status information is tracked by the MASTas follows. Initially, the MAST receives a Mobile Registration messagevia a registration notification forwarding mechanism, alternativelyreferred to as a Registration Forward Message, from the relevant MSC/HLR(I-HLR or S-HLR), and appropriately updates the activity status in thedatabase. Upon power down of the relevant wireless device, the MAST willreceive a Mobile De-Registration message via a Mobile Inactive Trigger(MIT) from the relevant MSC/HLR, and appropriately updates the activitystatus in the database.

[0102] When a new message (e.g., a mobile registration message or mobilede-registration message) is received, the MAST application preferablyparses the message, e.g., into up to 10 parameters, and stores theparsed message portions in an appropriate MSID ordered table.

[0103]FIG. 8 shows an exemplary Mobile Station Identity (MSID) orderedtable is shown in FIG. 8.

[0104]FIG. 9 shows an exemplary process by which the parsed messageportions are processed.

[0105] In particular, as shown in step 202 of FIG. 9, the processdetermines if a new REGNOT or MSINACT has been received.

[0106] If a record for the same MSID is found in the table of FIG. 8, instep 204 a comparison of the status and key parameters within the tworecords will be made.

[0107] In step 208, if the status (ACT to DEACT or DEACT TO ACT) or oneof the key parameters are different from that of the previous record, asubset of key parameters up to and including all key parameters fromthis new record will be sent to at least one, but possibly multiple IPaddresses on a network.

[0108] In steps 206 and 210, the old record is replaced in the MSIDtable with the new, most recent record.

[0109] The MAST receives information directly from the HLR or the STP(e.g., I-HLR or S-HLR), which has previously validated the MSID anddetermined the need to forward the information to the MAST.

[0110] Administration of the MAST may include, e.g., configuration andmaintenance of the following:

[0111] Point-codes and Subsystem numbers of the I-HLRs that will sendinformation to the MAST SPA.

[0112] Parameters that the I-HLR will forward to the MAST SPA in theregistration notification forwarding mechanism and MIT messages.

[0113] Parameters that the MAST SPA will forward to the applicationservers.

[0114] Destination IP addresses and Port numbers of the applicationservers.

[0115] Expiration time for records that have not experienced changesover a configurable period of time.

[0116] Size of the rotating log file.

[0117] There is preferably only one record per MSID in the MAST. Therelevant service provider is preferably given access to the databasestored in the MAST, e.g., through the conventional operationalmaintenance processor (OMP).

[0118] Due to its nature, the content of this database is likely tochange rapidly over time, therefore the MAST database may provide only asnapshot of the activity status of all the relevant wireless devices atany given time.

[0119] The MAST preferably keeps a temporary log of the messages sent tothe application services in a rotating file. This rotating file may havea configurably fixed size, and may overwrite itself with more recentinformation, e.g., after a desired period of time determined by thelevel of message traffic. This log provides a historical representationof the activity of specific wireless devices, or groups of wirelessdevices.

[0120] Reports may be generated for the relevant service provider, e.g.,through the OMP or via a TCP/IP connection to the Internet. Possiblereports can include, e.g., various information depending upon theparameters that the relevant HLR sends to the MAST, and/or specificneeds and selections made by the particular service provider.

[0121] In case the subscriber base increases, the platform can be easilyscaled to increase capacity.

[0122] Being a Wireless Intelligent Network service, MAST takesadvantage of the improved reliability, scalability and performance ofthe Advantage Platform and the flexibility of the intelligent networkapproach.

[0123] Additionally, MAST is an Intelligent Network application that canbe executed simultaneously on a single SCP platform, such as a ShortMessage Service Center, Over The Air Activation, PrePaid Wireless, etc.This fact spreads the cost of the platform over several services, thusallowing the service provider to price them in a competitive way. Froman operating standpoint, a single platform is easier to manage resultingin reduced maintenance costs.

Mobile Chat Location Register (MCLR)

[0124] The principles of the present invention may be used to implementa wireless chat tracking system (i.e., Mobile Chat Location Register(MCLR)) which utilizes a change in mobile registration status toautomatically notify a chat group system outside the wireless network ofcurrent status information activity regarding a relevant device, e.g.,registration activity or inactivity timeout.

[0125] In a disclosed embodiment, a registration notification (REGNOT)message is either explicitly forwarded or copied to an external IP basedapplication (e.g., to a mobile chat group system). The change in mobileregistration is communicated via a suitable signaling link (e.g., SS7,TCP/IP, etc.) between a Home Location Register (HLR) and the chat groupsystem. Therefore, instead of a conventionally closed system using SS7messages, REGNOT messages are pushed out over TCP/IP connections toexternal applications (e.g., chat servers) to automatically notify theexternal system of the location of a particular user.

[0126] In accordance with the principles of the present invention, aREGNOT message may be simply forwarded in accordance with instructionsfrom an HLR, or all REGNOT messages received may be copied and forwardedto an external application, which then sifts through the copied andreceived REGNOT messages for messages of relevance to that particularexternal application.

[0127]FIG. 12 shows an exemplary service implementation showing wirelesschat status tracking providing an automatic on-line or off-linenotification in a chat scenario using techniques and apparatus inaccordance with the principles of the present invention. FIG. 13 shows amore detailed block diagram of the SMSC 1230 shown in FIG. 12, includinga REGNOT message receiver 1304, a REGNOT forwarder 1302, and an optionalREGNOT copier 1306.

[0128] For the purposes of illustration, assume that in FIGS. 12 and 13all chat subscribers with the exception of Mobile A are alreadyparticipating in a chat session called, e.g., “Buddies”.

Scenario 1 Automatic On-Line Notification Chat Scenario in a PrepaidEnvironment

[0129] (1) The handset Mobile A 1202, provisioned with chat service, ispowered on or performs the IS-41 periodic or forced registrationprocess. Thus, a Registration access message is sent from the Mobile A1202 to the Mobile Switching Center (MSC) 1204.

[0130] (2) The MSC 1204 sends the IS-41 Registration Notification(REGNOT) message to the Home Location Register (HLR) 1206.

[0131] (3) Following the authentication process of Mobile A 1202, inaccordance with the principles of the present invention, the HLR 1206forwards the REGNOT message to, e.g., a relevant prepaid applicationserver. This may be performed using an IS-41 REGNOT message over an SS7network or an equivalent registration message over a TCP/IP network.

[0132] (4) The SMSC/Prepaid service 1230 may notify a suitable wirelessInternet gateway 1210 that Mobile A 1202 is “on-line”. Such a suitablewireless Internet gateway 1210 is shown and described in co-pending U.S.appl. Ser. No. 09/630,762, entitled “Wireless Internet Gateway” toSmith, filed Aug. 2, 2000.

[0133] If Mobile A 1202 is a prepaid subscriber, the prepaid service mayverify an account balance for Mobile A 1202 at this point and can decideto continue service or not.

[0134] (5) The wireless Internet gateway 1210 forwards the REGNOTmessage to a relevant external chat server 1220 automatically indicatingto that external application that Mobile A 1202 is “on-line”.

[0135] (6) The external chat server 1220 determines that Mobile A 1202belongs to a particular chat group, e.g., the chat group “Buddies” ofthe current example, and automatically registers Mobile A 1202 in thechat session.

[0136] (7) The external chat server 1220 notifies the other chatparticipants (e.g., the “Buddies” participants) that Mobile A 1202 isavailable by sending a broadcast text message to all currentparticipants of that chat session. At the same time, the chat server1220 may also notify Mobile A 1202 of all current participants of thatchat session.

[0137] (8) The wireless Internet gateway 1210 automatically forwardschat messages from the chat server 1220 for delivery to the chat sessionparticipants via the relevant SMSC 1230.

[0138] (9) The short message service center (SMSC) 1230 requests the HLR1206 for short message delivery to all participating mobile subscribers.

[0139] (10) The HLR 1206 provides the SMSC 1230 with all neededinformation to deliver the short messages.

[0140] (11) The SMSC 1230 stores and forwards the broadcast message tothe MSC 1204 for delivery to the other chat participants (e.g., toMobile B 1242 and Mobile C 1252), and the list of chat participantsmessage to the automatically entering Mobile A 1202.

[0141] (12) The MSC 1204 delivers the chat messages to all participatingmobiles 1202, 1242, 1252.

Scenario 2 Automatic Off-Line Notification Chat Scenario in a PrepaidEnvironment

[0142] (1) The handset Mobile A 1202, provisioned with chat service, ispowered off or has moved out of the relevant coverage area.

[0143] (2) The MSC 1204 detects an expiration of an inactivity timer andsends an IS-41 Inactivity message to the Home Location Register (HLR)1206.

[0144] (3) The HLR 1206 forwards the Inactivity message, e.g., the IS-41MS Inactivity message, over an SS7 network, or an equivalent inactivitymessage over a TCP/IP network to, e.g., a relevant prepaid applicationserver such as the SMSC/Prepaid platform 1230.

[0145] (4) The SMSC/Prepaid service 1230 notifies the wireless Internetgateway 1210 that Mobile A 1202 is “off-line”.

[0146] (5) The wireless Internet gateway 1210 forwards the message tothe chat server 1220 that Mobile A 1202 is “off-line”.

[0147] (6) The external chat server 1220 determines that Mobile A 1202belongs to, e.g., the chat group “Buddies”, and thus removes Mobile A1202 from the chat session.

[0148] (7) The external chat server 1220 notifies the chat sessionparticipants, e.g., participants of the chat session “Buddies”, thatMobile A 1202 has become unavailable, by sending a broadcast textmessage to all current chat participants.

[0149] (8) The wireless Internet gateway 1210 forwards the messages fordelivery.

[0150] (9) The SMSC 1230 requests the HLR 1206 for short messagedelivery to all mobile subscribers.

[0151] (10) The HLR 1206 provides the SMSC 1230 with all neededinformation to deliver the messages.

[0152] (11) The SMSC 1230 stores and forwards the broadcast message fordelivery to Mobile wireless devices B & C, 1242 & 1252.

[0153] The MSC 1204 delivers the messages to Mobile wireless devices B &C, 1242 & 1252.

[0154] Note that while the chat server 1220 shown in FIG. 12 is internalto the service provider's network, the principles of the presentinvention relate equally to placement of the chat server 1220 externalto the service provider's network, i.e., over the Internet 1299.

[0155] This solution may be integrated with existing, commerciallyavailable SMSC & web gateway products that enable wireless carriers &Internet service providers (ISPs) to offer, e.g., a pre-payment billingoption for enhanced messaging services.

[0156] The principles of the present invention have applicability forusage with wireless intelligent network (WIN) applications, e.g., thosealready otherwise containing SMSC, prepaid, and/or web gatewayapplications. Moreover, there is applicability for usage with mobileregistration, for inactivity message forwarding to a chat server, or formobile automatic notification of subscriber status to chat server.

[0157] While the invention has been described with reference to theexemplary embodiments thereof, those skilled in the art will be able tomake various modifications to the described embodiments of the inventionwithout departing from the true spirit and scope of the invention.

What is claimed is:
 1. In a short message service center, a module forpermitting automatic status tracking of a wireless chat participant byan application external to a service provider including said shortmessage service center, a message handler comprising: a registrationnotification message receiver; and a registration notification messageforwarder to forward a registration notification message received by amobile switching center over an Internet connection.
 2. In a shortmessage service center, a module for permitting automatic statustracking of a wireless chat participant by an application external to aservice provider including said short message service center, a handleraccording to claim 1 , wherein: said internet connection utilizes aTCP/IP protocol.
 3. In a short message service center, a module forpermitting automatic status tracking of a wireless chat participant byan application external to a service provider including said shortmessage service center, a handler according to claim 1 , wherein: saidregistration notification message forwarder copies all registrationnotification messages received by said mobile switching center.
 4. In ashort message service center, a module for permitting automatic statustracking of a wireless chat participant by an application external to aservice provider including said short message service center, a handleraccording to claim 1 , further comprising: a wireless Internet gatewayto transmit said forwarded notification message over said Internetconnection.
 5. In a short message service center, a module forpermitting automatic status tracking of a wireless chat participant byan application external to a service provider including said shortmessage service center, a handler according to claim 4 , wherein: saidregistration notification message handler communicates with saidwireless Internet gateway using a Signaling System #7 communicationsprotocol.
 6. In a short message service center, a module for permittingautomatic status tracking of a wireless chat participant by anapplication external to a service provider including said short messageservice center, a handler according to claim 1 , wherein: saidregistration notification message is previously forwarded by a HomeLocation Register (HLR).
 7. In a short message service center, a modulefor permitting automatic status tracking of a wireless chat participantby an application external to a service provider including said shortmessage service center, a message handler comprising: an MSInactivitymessage receiver; and an MSInactivity message forwarder to forward anMSInactivity message received by a mobile switching center over anInternet connection.
 8. In a short message service center, a module forpermitting automatic status tracking of a wireless chat participant byan application external to a service provider including said shortmessage service center, a handler according to claim 7 , wherein: saidinternet connection utilizes a TCP/IP protocol.
 9. In a short messageservice center, a module for permitting automatic status tracking of awireless chat participant by an application external to a serviceprovider including said short message service center, a handleraccording to claim 7 , wherein: said MSInactivity message forwardercopies all MSInactivity messages received by said mobile switchingcenter.
 10. In a short message service center, a module for permittingautomatic status tracking of a wireless chat participant by anapplication external to a service provider including said short messageservice center, a handler according to claim 7 , further comprising: awireless Internet gateway to transmit said forwarded MSInactivitymessage over said Internet connection.
 11. In a short message servicecenter, a module for permitting automatic status tracking of a wirelesschat participant by an application external to a service providerincluding said short message service center, a handler according toclaim 10 , wherein: said MSInactivity message handler communicates withsaid wireless Internet gateway using a Signaling System #7communications protocol.
 12. In a short message service center, a modulefor permitting automatic status tracking of a wireless chat participantby an application external to a service provider including said shortmessage service center, a handler according to claim 7 , wherein: saidMSInactivity message is previously forwarded by a Home Location Register(HLR).
 13. A method for automatically notifying an external chat serverof a presence of a chat session participant, comprising: receiving anIS-41 conforming registration notification message from a mobileswitching center; and automatically forwarding said IS-41 conformingregistration notification message over an Internet connection to anexternal chat server.
 14. The method for automatically notifying anexternal chat server of a presence of a chat session participantaccording to claim 13 , wherein: said registration notification messageis a REGNOT message.
 15. The method for automatically notifying anexternal chat server of a presence of a chat session participantaccording to claim 13 , wherein: said Internet connection utilizes aTCP/IP protocol.
 16. The method for automatically notifying an externalchat server of a presence of a chat session participant according toclaim 13 , wherein: said registration notification message isadditionally forwarded by an SMSC.
 17. The method for automaticallynotifying an external chat server of a presence of a chat sessionparticipant according to claim 13 , further comprising: automaticallyadding a user corresponding to said automatically forwarded registrationnotification message to a chat session.
 18. The method for automaticallynotifying an external chat server of a presence of a chat sessionparticipant according to claim 17 , further comprising: automaticallynotifying other chat participants regarding a presence of theautomatically added user.
 19. The method for automatically notifying anexternal chat server of a presence of a chat session participantaccording to claim 17 , further comprising: automatically sending a listof chat participants to said user.
 20. The method for automaticallynotifying an external chat server of a presence of a chat sessionparticipant according to claim 13 , wherein: said registrationnotification message is signaling system #7 and IS-41 compliant.
 21. Themethod for automatically notifying an external chat server of a presenceof a chat session participant according to claim 13 , wherein: saidregistration notification message is IS-41 compliant.
 22. Apparatus forautomatically notifying an external chat server of a presence of a chatsession participant, comprising: means for receiving an IS-41 conformingregistration notification message from a mobile switching center; andmeans for automatically forwarding said IS-41 conforming registrationnotification message over an Internet connection to an external chatserver.
 23. The apparatus for automatically notifying an external chatserver of a presence of a chat session participant according to claim 22, wherein: said registration notification message is a REGNOT message.24. The apparatus for automatically notifying an external chat server ofa presence of a chat session participant according to claim 22 ,wherein: said Internet connection utilizes a TCP/IP protocol.
 25. Theapparatus for automatically notifying an external chat server of apresence of a chat session participant according to claim 22 , furthercomprising: means for forwarding said registration notification messageby an SMSC to said means for automatically forwarding.
 26. The apparatusfor automatically notifying an external chat server of a presence of achat session participant according to claim 22 , further comprising:means for automatically adding a user corresponding to saidautomatically forwarded registration notification message to a chatsession.
 27. The apparatus for automatically notifying an external chatserver of a presence of a chat session participant according to claim 26, further comprising: means for automatically notifying other chatparticipants regarding a presence of the automatically added user. 28.The apparatus for automatically notifying an external chat server of apresence of a chat session participant according to claim 26 , furthercomprising: means for automatically sending a list of chat participantsto said user.
 29. The apparatus for automatically notifying an externalchat server of a presence of a chat session participant according toclaim 22 , wherein: said registration notification message is signalingsystem #7 and IS-41 compliant.
 30. The apparatus for automaticallynotifying an external chat server of a presence of a chat sessionparticipant according to claim 22 , wherein: said registrationnotification message is IS-41 compliant.
 31. A method for automaticallynotifying an external chat server of a presence of a chat sessionparticipant, comprising: receiving an IS-41 conforming MSInactivitynotification message from a mobile switching center; and automaticallyforwarding said IS-41 conforming MSInactivity message over an Internetconnection to an external chat server.